Unified identity verification

ABSTRACT

Apparatus, systems, and methods are disclosed that operate to register one time, at a server associated with an authenticating entity, information comprising an identity uniquely associated with an individual account owner and an account held by the authenticating entity. Further activity includes receiving an authentication request at the server from a requesting party to authenticate an unauthenticated individual purporting to be the individual account owner, and authenticating, by the server, the unauthenticated individual as the individual account owner by matching a token presented by the unauthenticated individual, to the identity. Responsive solely to the authenticating, only a selected portion of the information previously authorized by the individual account owner is provided for sharing with the plurality of selected requesting parties. Additional apparatus, systems, and methods are disclosed.

PRIORITY CLAIMS

This application is a continuation of U.S. Non-Provisional patent application Ser. No. 11/962,757, filed Dec. 21, 2007, which application in turn claims the benefit of the filing date of U.S. Provisional Patent Application No. 60/981,408, filed on Oct. 19, 2007. Both applications are commonly assigned to the assignee of the instant application, eBay Inc., and each is incorporated herein by reference in its entirety.

BACKGROUND

The Internet and the World Wide Web (“Web”) have changed the landscape of information delivery and affected numerous faculties of life, including electronic commerce and entertainment. One area that has benefited from this technological development is the ability for individuals to buy and sell products over the Internet. The resulting growth of electronic commerce has encouraged many businesses to join hands in doing business and in sharing customers and their information. The overlapping businesses, partnerships in conducting business, referrals, mutual distribution of resources, and sharing of users and user information has created a network of applications, servers, and Websites which has created various technical challenges, complexities, and insecurities.

BRIEF DESCRIPTION OF THE DRAWINGS

Some embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings in which:

FIG. 1 is a high level diagram illustrating token generation and authentication according to various embodiments of the invention.

FIG. 2 is a simplified diagram illustrating an example graphical user interface according to various embodiments of the invention.

FIG. 3 is a block diagram illustrating another example of a graphical user interface according to various embodiments of the invention.

FIG. 4 is a block diagram of apparatus and systems according to various embodiments of the invention.

FIG. 5 is a flow diagram illustrating methods according to various embodiments of the invention.

FIG. 6 is a flow diagram illustrating additional methods according to various embodiments of the invention.

FIG. 7 is a block diagram illustrating a client-server architecture to facilitate authentication according to various embodiments of the invention.

FIG. 8 is a block diagram of a machine in the example form of a computer system according to various embodiments of the invention.

DETAILED DESCRIPTION

The inventors have discovered that a number of technical challenges exist with respect to authorization and authentication of users and/or systems. For example, conventionally, when a customer attempts to make a purchase from a vendor that has not been previously approached, much sensitive and personal user information, ranging from passwords to profiles, is directly transmitted from the customer to the vendor. The transmission of such data is not only potentially insecure, but cumbersome, in that it may require a separate transmission for each of the secondary systems (i.e., servers) that the customer accesses, even when ultimately accessing the same primary system (e.g., vendor internet system provider). This and other technological challenges tend to limit the performance of system networks, in general, and the ability of the user to access multiple systems, in particular. Finally, it has been discovered by the inventors that many individuals are generally annoyed with having to verify their identity numerous times, even to the extent of providing the same information to entities which are directly related to each other.

To address these challenges and others, a mechanism has been developed so that an individual need register their identity only once, to a single entity, and thereafter, other entities may rely upon authentication by the entity that has registered the individual whenever the identity of the individual is to be verified. This can result in minimal transfer of information by an individual each time verification takes place. In addition, the individual can specify the information that may be released by the authenticating entity to other entities that seek identity verification.

Example System Architecture

FIG. 1 is a high level diagram illustrating token generation and authentication according to various embodiments of the invention. Prior to making a request for authentication, an individual should register once with some authenticating entity, such as a financial entity, so that their identity can later be verified. Once that occurs, the authenticating entity, perhaps represented by a financial entity server 112, can generate authentication tokens on behalf of the individual that has been registered.

For example, an individual may use a client terminal 108, perhaps taking the form of a cellular telephone in some embodiments, to inform the financial entity server 112 that authentication tokens have been requested in a requesting message 118. Upon the entry of selected information (e.g., logging into a bank account owned by the individual with a username and password), the authenticating entity may then generate and issue one or more tokens to the individual. Such tokens may take the form of one or more smart cards, a magnetic card, a radio frequency identification (RFID) device, a bar code, or a printed piece of paper. Thus, tokens may be physically generated, or electronically generated, perhaps in the form of an email message 120 to the terminal 108.

Once the tokens have been generated, they may be presented at a number of locations for authentication. In this manner, the individual need only register one time with an authenticating entity, and thereafter, authentication may be accomplished using tokens, so that little or no information is passed on to various other entities (e.g., an unknown vendor) for inspection prior to various transactions taking place.

Here it can be seen that a system 100 for token generation and authentication may receive a token 104, and a request 106 to authenticate the token 104, perhaps at an internet service provider (ISP) server 110 representing a vendor or other party requesting authentication of the token 104. The request for authentication of the token 104 may be entered using a client terminal 116 with a graphical user interface (GUI) 102. One example of such a request might be initiated by scanning a smart card having an embedded RFID device with the token recorded thereon. Another might be scanning a bar code, either as presented by a customer on a printed piece of paper, or perhaps, as displayed on a cellular telephone.

Responsive to receiving the request, the ISP server 110 may forward the token 104 as part of a message 144 to a financial entity server 112. The financial entity server 112 may represent the financial entity or other entity that has registered the identity of the individual seeking authentication by the vendor (represented by the ISP server 110). If the token is matched by the financial entity server, then a message 148 announcing that authentication was successful may be returned to the ISP server 110 from the financial entity server 112, and thereafter, to the client terminal 116.

FIG. 2 is a simplified diagram illustrating an example graphical user interface 200 according to various embodiments of the invention This interface 200 is one of many that are possible. In the particular example of FIG. 2, a sample web page that might be seen by an individual that has logged into his bank account on the Internet is shown. Here, the “TOKEN” option 204 has been selected, calling up the TOKEN GENERATION PAGE 208. This selection permits the individual account owner to select a particular account 212 that can be used to generate tokens. Here it can be seen that several fields, such as a time limit field 216, a number presented field 220, and a vendor list field 240 may be populated with various information.

For example, after an individual selects an account 212 to be used in conjunction with token generation, perhaps from a number of accounts in an account field 232, a time limit for token validity may be set in field 216 (e.g., 24 hours after generation, the token will no longer be valid for authentication purposes). The individual may also select how many times the token may be presented (e.g., 10) using the field 220. Finally, a limited selection of entities that can request authentication may also be selected, using field 240. In this way, the useful lifetime and other breadth of use characteristics for particular tokens may be limited, providing increased security. The individual may also specify information to be shared with requesting parties by the authenticating entity upon successful authentication, perhaps using the sharing field 236.

Once the limiting selections have been made, the individual account owner might simply click on the GENERATE widget 224 to generate a token. In some embodiments, a message field 228 in the GUI 200 may be used to inform the individual account owner when the last token was generated. Other fields in the GUI 200 may be used to provide additional selection alternatives.

FIG. 3 is a block diagram illustrating another example of a graphical user interface 300 according to various embodiments of the invention. This interface 300 is one of many that are possible. In the particular example of FIG. 3, a sample web page that might be seen by a vendor that has logged into an authentication entity web page on the Internet is shown. Here, the “VERIFY” option 344 has been selected, calling up the AUTHENTICATION PAGE 348. This selection permits the vendor (e.g., the requesting party) to enter a token into an authentication system by a number of methods, including manually typing in a coded value into the token field 352. Other methods of entry include electrical (e.g., direct contact pads), electronic (e.g., RFID), and optical (e.g., bar code) scanning.

The time and date may be entered into the time/date field 316, and the party making the request may identify themselves in the vendor field 320. The authentication entity may be selected using the verification field 340. For security purposes, any of the fields 352, 316, 320, and 340 may be auto-generated by the authenticating entity.

To authenticate the token, the requesting party might simply click on the AUTHENTICATE widget 324. The validity of the token (and therefore authentication of the identity of the individual, such as a customer of the vendor) may be indicated by simple GO, NO-GO or GOOD/BAD indicators. Upon successful authentication, certain information 332 may be shared with the requesting party. Here, for example, the name, physical address, and the email address of the individual are shared. Other information, obtained at the time of registration or thereafter by the authenticating entity, may also be shared, if requested by the requesting party and permitted by the individual. Such information may be specified as part of the token generation activity (shown in FIG. 2). In some embodiments, a message field 328 in the GUI 300 may be used to inform the requesting party when the last authentication occurred, either with respect to the particular token being authenticated, or perhaps with respect to the vendor requesting authentication.

FIG. 4 is a block diagram of apparatus 402 and systems 410 according to various embodiments of the invention. The apparatus 402 can take many forms, such as an automated teller machine (ATM), a cellular telephone, a desktop computer terminal with Internet access, a point of sale (POS) terminal, etc.

In some embodiments, the apparatus 402 may comprise one or more user input devices 408, such as a voice recognition processor 416, a keypad 420, a touchscreen 424, a scanner 426, a thumbwheel, a button, etc. In some embodiments, a POS terminal may be used to house the user input device 408.

The apparatus 402 may include a client module 432 to communicatively couple to a server (e.g., server 430) at a financial entity. The apparatus 402 may also comprise an authentication request module 428 to receive a token 414 presented by a customer, to transmit a request 448 to the financial entity (e.g., represented by the server 430) to authenticate the customer purporting to be a particular individual, and to receive notification 458, from the financial entity, that the customer is authenticated as the individual based on matching the token 414 to an identity that has been registered with the financial entity and is uniquely associated with the individual.

Other embodiments may be realized. For example, a system 410 may include one or more apparatus 402. The system 410 may also include a server 430 to communicatively couple to a global computer network 418 (e.g., the Internet), and an authentication module 438 to receive a request 448 from a requesting party (e.g., represented by the client terminal 402) to authenticate the customer purporting to be a particular individual. The request 448 may include the token 414.

The authentication module 438 may be used to send notification 458 that the customer is authenticated as the individual based on matching the token 414 to an identity that has been registered with a financial entity and is uniquely associated with the individual. For example, the server 430 may be located within a bank that has many individual account holders, each registered so that identity authentication tokens 414 may be generated on their behalf.

As noted previously, the terminal 402 may comprise a POS terminal associated with the requesting party, wherein the POS terminal is to receive the token 414, and to be communicatively coupled to the server 430. In some embodiments, the system 410 may comprise a storage device 450 to couple to the server 430 and to store a database 454 having a plurality of registered identities IDENTITIES, including the identity of the individual whose identity is being authenticated.

Example Methods

FIG. 5 is a flow diagram illustrating methods 511 according to various embodiments of the invention. For example, a computer-implemented method 511 may begin at block 513 with registering one time, at an authenticating entity, information comprising an identity uniquely associated with an individual having a financial account held by the financial entity.

Registering at block 513 may include obtaining, verifying, and recording the information according to customer identification program (CIP) requirements, Know Your Customer (KYC) requirements, Know Your Business (KYB) requirements, and watch-list scanning requirements. Such requirements are well-known to those of ordinary skill in the art. The information may comprise one or more of the name of the individual, the birth date of the individual, the physical address associated with the individual, and/or an identification number associated with the individual (e.g., social security number, hash-coded identification number, etc.). Registering may also comprise obtaining, verifying, and recording a prior verification associated with the customer by the financial entity against customer identification program (CIP) requirements, Know Your Customer (KYC) requirements, Know Your Business (KYB) requirements and watch-list scanning requirements, for example.

The method 511 may continue on to block 521 with receiving a request at the authenticating entity from a requesting party that has been presented with a token to authenticate a customer purporting to be a particular individual. The requesting party may comprise a vendor, another financial entity, a brokerage, a lender, a car lot, an online auction provider, etc. Receiving the request may include receiving a message from the requesting party at the authenticating entity via a global computer network (e.g., the Internet).

At this point, an attempt is made to match the token presented to the identity of the individual. Thus, the method 511 may include at block 525 authenticating, by the authenticating entity, such as a bank or other financial entity, the customer as the individual by matching a token presented by the customer to the identity uniquely associated with the individual. If no match is determined at block 525, the method 511 may include requesting, if the authenticating is not successful, additional information from the customer at block 529. One or more additional attempts, perhaps limited in number by the authenticating entity, may be made to authenticate the identity of the individual by matching the token with the identity at 525.

If authentication succeeds at block 525, the method 511 may include notifying the requesting party that the customer has been authenticated as the individual by sending a message (e.g., an email message) to the requesting party, perhaps via a global computer network, at block 533. For example, the method 511 may include sending a message to a mobile device associated with the customer that the authenticating has been successful. This mobile device may also be used to present the token for authentication, perhaps by transmitting it electronically, or by displaying a bar code image on its display screen (e.g., a personal digital assistant (PDA) or cellular phone display).

The method 511 may go to include, at block 535, storing the information in an authentication database. For security reasons, the authentication database may be linked to, but physically separate from, a database of accounts including a financial account associated with the individual whose identity is being authenticated.

At this point, the method 511 may include providing to the requesting party a portion of a profile associated with the individual, which the individual previously authorized the financial entity to share (e.g., name, physical address, social security number, email address, telephone number, etc.).

In some embodiments, the method 511 includes generating one or more tokens by a financial entity (or any other authentication entity) upon request by the individual at block 541. Generating tokens at block 541 may include generating tokens having: one or more of an expiration time period after which presentation of the token by the customer is ineffective, a selected number of requesting parties to which the token may be presented, a selected number of times the token may be presented, and named requesting parties to whom the token may be presented. Other limitations may be imposed.

The method 511 may go on to block 545 with transmitting the token to the individual. Transmitting may comprise sending an email message, perhaps including the token, to the individual.

In some embodiments, the method 511 may include receiving funds from a customer, such as an amount associated with a transaction, or some other amount, at block 549. Thus, for example, the method 511 may include establishing a new account at a bank associated with an authenticated individual to hold the funds without receiving any further information from the customer at block 551. That is, a new account may be opened at a financial entity that is not the authenticating entity, solely on the basis of authenticating the identity of an individual using a token. Another example includes receiving an amount associated with a transaction associated with a vendor at block 549, and substantially simultaneously extending credit at block 555 to the customer by the authenticating entity (e.g., a financial entity), on behalf of the vendor, based on authenticating the identity of a particular individual, using the token.

FIG. 6 is a flow diagram illustrating additional methods 611 according to various embodiments of the invention. In some embodiments, a computer-implemented method 611 may begin at block 613 with receiving a token presented by a customer, which may in turn comprise receiving a password entry at a terminal, for example. At substantially the same time the token is received, permission to share selected information from the profile associated with the customer may also be received. Such permission may be entered by the customer into the same terminal as that used to receive the token. Thus, receiving at block 613 may include receiving the token in conjunction with permission to receive additional information associated with the individual. In this way, the customer has the option, in some embodiments, of permitting additional information to be shared with the vendor, even after a token is generated. Such additional information might include one or more of the name of an authenticated individual, the birth date of the individual, the physical address associated with the individual, and an identification number associated with the individual (e.g., driver's license or other license number associated with the individual).

The method 611 may go on to include transmitting a request to an authenticating entity, such as a financial entity, to authenticate the customer purporting to be a particular individual at block 617. At this point, an attempt is made to match the token to the identity registered for the individual at the authenticating entity.

If a match between the token and the identity is not obtained at block 625, then the method 611 may terminate at block 627. Of course, repeated attempts to authenticate may also occur, as shown in FIG. 5.

If the token is found to match the identity at block 625, then the method 611 may include receiving notification from the financial entity (or other authenticating entity) at block 641, that the customer is authenticated as the individual based on matching the token to an identity that has been registered with the financial entity and is uniquely associated with the individual.

In some embodiments, if the requesting party is a vendor, for example, the method 611 may include substantially simultaneously extending credit to the customer by the vendor, responsive to the authenticating, at block 645. In some embodiments, the method 611 may include automatically transferring an amount to be paid from an account associated with the individual and held by the financial entity (e.g., credit card account at the authenticating entity) directly to an account associated with the requesting party. This is what might occur when purchases are made online or in a store, for example.

The methods 511, 611 described herein do not have to be executed in the order described, or in any particular order. Moreover, various activities described with respect to the methods identified herein can be executed in repetitive, serial, or parallel fashion. Information, including parameters, commands, operands, and other data, can be sent and received in the form of one or more carrier waves.

One of ordinary skill in the art will understand the manner in which a software program can be launched from a computer-readable medium in a computer-based system to execute the functions defined in the software program. Various programming languages may be employed to create one or more software programs designed to implement and perform the methods disclosed herein. The programs may be structured in an object-orientated format using an object-oriented language such as Java or C++. Alternatively, the programs can be structured in a procedure-orientated format using a procedural language, such as assembly or C. The software components may communicate using a number of mechanisms well known to those skilled in the art, such as application program interfaces or interprocess communication techniques, including remote procedure calls. The teachings of various embodiments are not limited to any particular programming language or environment.

Thus, other embodiments may be realized, including a machine-readable medium (e.g., the memories 434 of FIG. 4) encoded with instructions for directing a machine to perform operations comprising any of the methods described herein. For example, some embodiments may include a machine-readable medium encoded with instructions for directing a client terminal or server to perform a variety of operations. Such operations may include any of the activities presented in conjunction with the methods 511, 611 described above.

Example Network Architecture

FIG. 7 is a block diagram illustrating a client-server architecture to facilitate authentication according to various embodiments of the invention. The authentication system 700 comprises a client-server architecture used for registration, token generation and/or authentication. A financial platform, in the example form of a network-based financial system 702, provides server-side functionality, via a network 780 (e.g., the Internet) to one or more clients. FIG. 7 illustrates, for example, a web client 706 (e.g., a browser, such as the Internet Explorer browser developed by Microsoft Corporation of Redmond, Wash.), and a programmatic client 708 executing on respective client machines 710 and 712. In an example embodiment, either or both of the web client 706 and programmatic client 708 may include a mobile device.

Turning specifically to the network-based financial system 702, an Application Program Interface (API) server 714 and a web server 716 are coupled to, and provide programmatic and web interfaces respectively to, one or more application servers 718. The application servers 718 host one or more financial applications 720 and authentication applications 722 (e.g., similar to or identical to the authentication module 438 of FIG. 8). The application servers 718 are, in turn, shown to be coupled to one or more database servers 724 that facilitate access to one or more databases 726, such as registries that include links between individuals, their identity information, and/or financial entity accounts.

The financial applications 720 provide a number of financial functions and services to users that access the network-based financial system 702. The authentication applications 722 facilitate authenticating tokens presented by registered individuals.

Further, while the authentication system 700 shown in FIG. 7 employs a client-server architecture, the present application is of course not limited to such an architecture, and could equally well find application in a distributed, or peer-to-peer, architecture system. The various financial and authentication applications 720 and 722 may also be implemented as standalone software programs, which do not necessarily have networking capabilities.

The web client 706, it will be appreciated, may access the various financial and authentication applications 720 and 722 via the web interface supported by the web server 716. Similarly, the programmatic client 708 accesses the various services and functions provided by the financial and authentication applications 720 and 722 via the programmatic interface provided by the API server 714. The programmatic client 708 may, for example, comprise an authentication request module (e.g., similar to or identical to the authentication request module 428 of FIG. 4) to enable a user to request authentication and to perform batch-mode communications between the programmatic client 708 and the network-based financial system 702. Client applications 732 and support applications 734 may perform similar or identical functions.

Thus, the authentication system 700 may provide a number of registration, token generation, and authentication mechanisms whereby a user may receive tokens for authentication by any number of entities. The financial applications 720 may include one or more account management applications which support and provide services related to various user accounts in a financial entity (e.g. a bank). The various account management applications may also provide a number of features such as supervising account transfers, holding account balances, and keeping tracking of and reporting transactions to relevant applications.

The financial applications 720 may also include dispute resolution applications to provide mechanisms whereby disputes arising between transacting parties may be resolved. For example, the dispute resolution applications may provide guided procedures whereby the parties are guided through a number of steps in an attempt to settle a dispute. In the event that the dispute cannot be settled via the guided procedures, the dispute may be escalated to a customer service agent for the financial system 702, third party mediator, or arbitrator.

Example Machine Architecture

FIG. 8 is a block diagram, illustrating a diagrammatic representation of machine 900 in the example form of a computer system within which a set of instructions for causing the machine to perform any one or more of the methodologies discussed herein may be executed. The machine 900 may also be similar to or identical to the client terminal 402 or server 430 of FIG. 4.

In alternative embodiments, the machine 900 may operate as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine 900 may operate in the capacity of a server or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment.

The machine 900 may be a server computer, a client computer, a personal computer (PC), a tablet PC, a set-top box (STB), a PDA, a cellular telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

The example computer system 900 may include a processor 902 (e.g., a central processing unit (CPU), a graphics processing unit (GPU) or both), a main memory 904 and a static memory 906, all of which communicate with each other via a bus 908. The computer system 900 may further include a video display unit 910 (e.g., liquid crystal displays (LCD) or cathode ray tube (CRT)). The computer system 900 also may include an alphanumeric input device 912 (e.g., a keyboard), a cursor control device 914 (e.g., a mouse), a disk drive unit 916, a signal generation device 918 (e.g., a speaker) and a network interface device 920.

The disk drive unit 916 may include a machine-readable medium 922 on which is stored one or more sets of instructions (e.g., software 924) embodying any one or more of the methodologies or functions described herein. The software 924 may also reside, completely or at least partially, within the main memory 904 and/or within the processor 902 during execution thereof by the computer system 900, the main memory 904 and the processor 902 also constituting machine-readable media. The software 924 may further be transmitted or received over a network 926 via the network interface device 920, which may comprise a wired and/or wireless interface device.

While the machine-readable medium 922 is shown in an example embodiment to be a single medium, the term “machine-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “machine-readable medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present invention. The term “machine-readable medium” shall accordingly be taken to include tangible media that include, but are not limited to, solid-state memories and optical and magnetic media.

The machine 900 may use various hardware accelerators and security systems as part of the instructions 924 for performing ciphering and cryptography, including the Rivest-Shamir-Adleman (RSA) security algorithm and cryptography by RSA Security, Inc. located at Bedford, Mass., as well as the El Gamal algorithm by Taher El Gamal. The RSA implementation is also to implement RSA BSAFE implementation, which is a form of hardware accelerator, to support the BSAFE library interface. Alternative solutions include operating system platforms (e.g., OpenBSD) that are securely built into an operating system. The operating system platforms can dedicate a processor in a multiple-way hardware platform and are also configured to use one or more processors in a multi-processor system for cryptographic operations. The machine 900 may further use decryption and encryption in validating a token's sequence number to prevent other systems or sites from replaying or minting the token authentication module (see module 438 of FIG. 4).

Using the apparatus, systems, and methods disclosed herein may reduce the effort required to verify the identity of individuals at a number of entities, including stores, banks, online auctions, and the like. Increased customer satisfaction may result.

The accompanying drawings that form a part hereof, show by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

Such embodiments of the inventive subject matter may be referred to herein, individually and/or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description.

The Abstract of the Disclosure is provided to comply with 37 C.F.R. §1.72(b), requiring an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment. 

1. A computer-implemented method, comprising: registering one time, at a server associated with an authenticating entity, information comprising an identity uniquely associated with an individual account owner and an account held by the authenticating entity, wherein the registering includes receiving a user permission authorizing the authenticating entity to share a selected portion of the information with a plurality of selected requesting parties; receiving an authentication request at the server associated with the authenticating entity from a requesting party to authenticate an unauthenticated individual purporting to be the individual account owner, responsive to a request being provided by a client terminal associated with the unauthenticated individual to the requesting party; authenticating, by the server associated with the authenticating entity, the unauthenticated individual as the individual account owner by matching a token presented by the unauthenticated individual to the identity uniquely associated with the individual account owner; and responsive solely to the authenticating, providing from the server associated with the authenticating entity to the requesting party only the selected portion of the information previously authorized by the individual account owner to be shared with the plurality of selected requesting parties.
 2. The computer implemented method of claim 1, wherein registering one time comprises: generating the token for the individual account owner by the server of the authenticating entity; and transmitting the token to a client terminal associated with the individual account owner.
 3. The computer implemented method of claim 2, wherein generating the token comprises receiving, from the client terminal associated with the individual account owner, at least one of an expiration time period after which presentation of the token by the unauthenticated individual is ineffective, a selected number of requesting parties to which the token may be presented, or a selected number of times the token may be presented.
 4. The computer implemented method of claim 2, wherein the transmitting comprises sending an email message including the token to the individual account owner.
 5. The computer implemented method of claim 1, wherein the requesting party comprises a bank, further comprising: receiving funds from the unauthenticated individual; and establishing a financial account at the bank, the financial account associated with the individual account owner to hold the funds without receiving any further information from the unauthenticated individual.
 6. The computer implemented method of claim 1, wherein the requesting party comprises a vendor, further comprising: receiving an amount associated with the authentication request and the vendor; and substantially simultaneously extending credit to the unauthenticated individual by the authenticating entity, on behalf of the vendor, based on the authenticating.
 7. A computer-implemented method, comprising: receiving an authentication request at a server associated with an authenticating entity from a requesting party responsive to a request being provided to the requesting party by a client terminal associated with an unauthenticated individual purporting to be an individual account owner previously authenticated with the authenticating entity, the authentication request to authenticate the unauthenticated individual, the receiving the authentication request including receiving, at the server associated with the authenticating entity, a token from the client terminal associated with the unauthenticated individual, the token including information associated with the unauthenticated individual and a user permission authorizing the authenticating entity to share a selected portion of the information with a plurality of selected requesting parties, the user permission to be received during registration of the information comprising an identity to the server associated with the authenticating entity; authenticating, by the server associated with the authenticating entity, the unauthenticated individual as the individual account owner based on matching the token to the identity that has been registered with the authenticating entity and is uniquely associated with the individual account owner; and responsive solely to the authenticating, providing from the server associated with the authenticating entity to the requesting party only the selected portion of the information previously authorized by the individual account owner to be shared with the plurality of selected requesting parties.
 8. The computer-implemented method of claim 7, wherein the token comprises a password.
 9. The computer-implemented method of claim 7, further comprising automatically transferring an amount to be paid from a financial account associated with the individual account owner and held by the authenticating entity directly to a financial account associated with the requesting party.
 10. The computer-implemented method of claim 7, wherein the token associated with the individual account owner includes further information indicating the plurality of selected requesting parties.
 11. The computer-implemented method of claim 7, wherein the receiving the authentication request comprises: receiving from the client terminal associated with the unauthenticated individual an additional permission authorizing the authenticating entity to share an additional portion of the information with one or more of the plurality of the selected requesting parties.
 12. The computer-implemented method of claim 7, further comprising: automatically opening a new financial account for the unauthenticated individual at a financial entity responsive to the authenticating.
 13. The computer-implemented method of claim 7, further comprising: automatically extending credit to the unauthenticated individual by the requesting party responsive to the authenticating.
 14. An apparatus, comprising: a client module to communicatively couple to a server associated with an authenticating entity; and at least one processor to run an authentication request module configured to receive a token associated with a request from a client terminal associated with a unauthenticated individual, to transmit an authentication request to the authenticating entity to authenticate the unauthenticated individual purporting to be an individual account owner, to receive notification from the authenticating entity that the unauthenticated individual is authenticated as the individual account owner based on matching the token to an identity that has been registered with the authenticating entity one time, and is uniquely associated with the individual account owner and to receive, from the server associated with the authenticating entity, only a selected portion of information associated with the individual account owner responsive solely to the unauthenticated individual being authenticated as the individual account owner by the authenticating entity, wherein the selected portion of the information is previously authorized by the individual account owner to be shared between the authenticating entity and a plurality of selected requesting parties, during registration of the identity to the server associated with the authenticating entity.
 15. The apparatus of claim 14, wherein the token is included in at least one of a bar code or a radio frequency identification (RFID) device.
 16. The apparatus of claim 14, wherein the client terminal comprises a cellular telephone.
 17. A system, comprising: a server to communicatively couple to a global computer network; and an authentication module to register an individual account owner, the registering including receiving information associated with the individual account owner and receiving a user permission authorizing an authenticating entity associated with the server to share a selected portion of the information with a plurality of selected requesting parties, to receive an authentication request from a requesting party, the authentication request including a token presented by a client terminal associated with a unauthenticated individual, to authenticate the unauthenticated individual purporting to be the individual account owner responsive to a request being provided by the unauthenticated individual to the requesting party, and to send notification that the unauthenticated individual is authenticated as the individual account owner based on matching the token to an identity that has been registered with the authenticating entity and is uniquely associated with the individual account owner, the authentication module configured, responsive solely to the unauthenticated individual being authenticated as the individual account owner by the authenticating entity, to provide from the server to the requesting party only the selected portion of the information previously authorized by the individual account owner to be shared with the plurality of selected requesting parties.
 18. The system of claim 17, further comprising a point of sale (POS) terminal associated with the requesting party, wherein the POS terminal is to receive the token having limited breadth of use characteristics, the POS terminal to be communicatively coupled to the server.
 19. The system of claim 17, further comprising a storage device to communicatively couple to the server and to store a database having a plurality of registered identities, including the identity.
 20. A machine-readable device storing instructions, which when executed by one or more processors, cause the one or more processors to perform operations comprising: registering one time, at a server associated with an authenticating entity, information comprising an identity uniquely associated with an individual account owner and an account held by the authenticating entity, wherein the registering includes receiving a user permission authorizing the authenticating entity to share a selected portion of the information with a plurality of selected requesting parties; receiving an authentication request at the server associated with the authenticating entity from a requesting party to authenticate an unauthenticated individual purporting to be the individual account owner, responsive to a request being provided by a client terminal associated with the unauthenticated individual to the requesting party; authenticating, by the server associated with the authenticating entity, the unauthenticated individual as the individual account owner by matching a token presented by the unauthenticated individual to the identity uniquely associated with the individual account owner; and responsive solely to the authenticating, providing from the server associated with the authenticating entity to the requesting party only the selected portion of the information previously authorized by the individual account owner to be shared with the plurality of selected requesting parties.
 21. The machine-readable device of claim 20, wherein the instructions, when executed by the one or more processors, cause the one or more processors to further perform storing the information in an authentication database, linked to but physically separate from, a database of accounts including the account.
 22. The machine-readable device of claim 20, wherein the instructions, when executed by the one or more processors, cause the one or more processors to further perform sending a message to the client terminal associated with the unauthenticated individual that the authenticating has been successful, the client terminal comprising a mobile device.
 23. The machine-readable device of claim 22, wherein the instructions, when executed by the one or more processors, cause the one or more processors to further perform requesting, when the authenticating is not successful, additional information from the client terminal associated with the unauthenticated individual, the client terminal associated with the unauthenticated individual comprising a mobile device. 